Princípios de racionalização energética na arquitectura vernacular

A arquitectura vernacular caracteriza-se por materializar formalmente uma pluralidade de condicionalismos – geográficos, climáticos e económicos – dos locais onde se insere. Estas implicações traduzem-se na diferenciação regional das estratégias usadas para mitigar os efeitos do clima. Apesar das condições de conforto destas construções não se enquadrarem nos parâmetros actuais, as estratégias adoptadas apresentam potencial de evolução e adaptação à contemporaneidade. Na altura, a fragilidade económica de grande parte das famílias levava à adopção de soluções pragmáticas e de profunda racionalização dos recursos disponíveis. O abandono destas abordagens arquitectónicas em detrimento de uma arquitectura universal baseada em materiais industriais, desarraigada do seu meio, levou a um tipo de construção muito dependente de energia para se garantirem os requisitos de conforto dos ocupantes. Num momento de viragem, promovido pelos actuais contextos ambiental e económico, em que se procuram formas de energia mais limpas e edifícios mais eficientes, é pertinente voltar ao passado para estudar e compreender estas formas de construção intrínsecas ao lugar, com o intuito de adaptar e desenvolver as suas mais-valias na descoberta das formas do futuro

SPEM 2.0 extension for pervasive information systems

Pervasive computing is a research field of computing technology that aims to achieve a new computing paradigm. In this paradigm, the physical environment has a high degree of pervasiveness and availability of computers and other information technology (IT) devices, usually with communication capabilities. Pervasive Information Systems (PIS), composed by these kinds of devices, bring issues that challenge software development for them. Model-Driven Development (MDD), strongly focusing and relying on models, has the potential to allow: the use of concepts closer to the domain and the reduction of semantic gaps; higher automation and lower dependency to technological changes; higher capture of expert knowledge and reuse; an overall increased productivity. Along with the focus and use of models, software development processes are fundamental to efficient development efforts of successful software systems. For the description of processes, Software & Systems Process Engineering Meta-Model Specification (SPEM) is the current standard specification published by the Object Management Group (OMG). This paper presents an extension to SPEM (version 2.0) Base Plug-In Profile that includes stereotypes needed to support a suitable structural process organization for MDD approaches aiming to develop software for PIS. A case study is provided to evaluate the applicability of the extension

Teaching embedded systems engineering in a software-oriented computing degree

Traditional software-oriented computing degrees do not include courses on embedded systems design in their syllabus, since in the past embedded applications were seen as small-sized solutions developed without the need of engineering approaches. This reality has dramatically changed in the last decade and nowadays several embedded systems are quite complex. Embedded systems present several idiosyncrasies that make their development more difficult and complex than desktop solutions, namely when considering non-functional requirements, time-related deadlines, or the correctness of the solution. To be well prepared for their professions, students of software-oriented computing degrees must acquire skills and competencies in embedded systems engineering. Being able to master high-level programming languages and to develop solutions only for desktop computers means that the students cannot consider numerous opportunities, after graduation. This paper discusses which topics in embedded software design to include in a second cycle degree on Software Engineering that was structured to consider the Bologna Declaration that is now being used in Europe to recast all university degrees. The syllabus of a 15-ECTS module dedicated to teach the fundamental concepts of embedded systems engineering and embedded software development is also described

Object-oriented inheritance of statecharts for control applications

This paper discusses how object-oriented iuheritance can be re-interpreted if statecharts are used for modelling the dynamic behaviour of an object. The support of inheritance of statecharts allows the improvement of systems' development by easing the reutilization of parts of already developed euccessful systems, aad by promoting the iterative and continuous models' refinement advocated by the operatioaal approach. Statechart is the formalism used within UML to specify reactive state.based behaviours. This paper covers the use of statecharts within the modelling of embedded systems for industrial control applxications, where performance and memory usage are main concerns

A Petri net meta-model to develop software components for embedded systems

This paper presents a new Petri net (PN) meta-model, called shobi-PN v2.0, that can be used to specify the dynamic behaviour of concurrent systems, using object-oriented modelling concepts together with a generalised arc set capable of coping with the complexity of the current embedded systems. This new Petri net meta-model can also be used to support a component-based development approach in the design of generic and parametrisable control-oriented software components for embedded systems

A multi-level design pattern for embedded software

It is a common practice amongst programmers to construct parts of software programs by imitating parts of programs constructed by more experienced professionals. This “learn by example” approach can be applied at the design level by using patterns as sets of rules and recommendations to solve well defined tasks within the development of computer based systems. This paper describes the multi level ICIS pattern, to be used at various design levels of industrial control based information systems, where embedded devices are networked to interact with the industrial processes and equipment. The proposed pattern is described using several UML diagrams.Fundação oara a Ciência e Tecnologia; FEDER - project METHODES (POSI/37334/CHS/2001)

Projecto de hardware digital orientado por objectos

Os limites entre os domínios do software e do hardware são cada vez mais ténues, pelo que técnicas inicialmente experimentadas no software têm vindo a ser gradualmente aplicadas no hardware. Este artigo pretende descrever o estado actual da utilização da tecnologia de programação orientada por objectos no projecto de hardware digital. São analisadas as vantagens e implicações quando se introduzem conceitos ligados à tecnologia orientada por objectos em projectos de hardware e é apresentado um exemplo utilizando uma das extensões orientadas por objectos da linguagem VHDL.The boundaries between the software and hardware domains are no longer fixed, which enables the use, on the hardware domain, of techniques originally applied on software projects. This article aims to describe the stateof-the-art in the application of object-oriented programming techniques to digital hardware design. The advantages and implications of object-oriented technology concepts applied to hardware design are analyzed and an example with an object-oriented VHDL language extension is presented

Integration of embedded software with corporate information systems

This paper describes a methodology and corresponding tools to support the development of information systems, by integrating and interconnecting a network of embedded devices, that supervise processes in industrial environments, with the corporate information system of an organization. We discuss in detail how the LabVIEW environment was customized, so that it effectively supports a component based and data flow approach in the development of the gateway responsible for the integration

A two-year Software Engineering M.Sc. degree designed under the Bologna Declaration Principles

This paper presents and discusses the syllabus of a second cycle degree on Software Engineering in which any student that finishes any undergraduate Computing degree (Computer Engineering, Computer Science, Information Systems, Information Technology, and Software Engineering) can enroll. In the first year, the degree is composed of two 30 ECTS modules, one dedicated to software analysis and design and the other devoted to software quality and management. Each module is composed of five curricular units, being one of them dedicated to the experimental integration of the module’s topics. The second year allows two different paths to be followed by the students. The professional path includes a 30 ECTS industrial project, while in the scientific path students must write a 45 ECTS master dissertation. The degree is mainly structured to consider the Bologna Declaration that is now being used in Europe to recast all university degrees. Additionally, we also considered the Software Engineering 2004 Curriculum Guidelines and the Knowledge Areas described in the SWEBOK.(undefined

Development framework pattern for pervasive information systems

During last decade, the world watched a social acceptance of computing and computers, enhanced information technology devices, wireless networks, and Internet; they gradually became a fundamental resource for individuals. Nowadays, people, organizations, and the environment are empowered by computing devices and systems; they depend on services offered by modern Pervasive Information Systems supported by complex software systems and technology. Research on software development for PIS-delivered information, on issues and challenges on software development for them, and several other contributions have been delivered. Among these contributions are a development framework for PIS, a profiling and framing structure approach, and a SPEM 2.0 extension. This chapter, revisiting these contributions, provides an additional contribution: a pattern to support the use of the development framework and profiling approach on software development for PIS. This contribution completes a first series of contributions for the development of PIS. This chapter also presents a case study that allowed demonstrating the applicability of these contribution